LogsView wraps itself in its own NavigationStack and is pushed inside
the Settings tab's stack. SwiftUI's behaviour with nested
NavigationStacks is inconsistent: NavigationLink(value:) pushes from
inside the nested stack can silently route to the *outer* stack,
which in this case had no DeviceRoute / GroupRoute handler. Result:
tapping the device/group hero card on a log opened via Settings → Logs
did nothing — the user perceived it as being dropped back to the tab
root.

Register the same handlers on SettingsView and BridgeSettingsView
NavigationStacks as a safety net so the push lands correctly no matter
which enclosing stack SwiftUI picks. The handlers inside LogsView's own
stack are kept too, so the in-tab Logs path also still works.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>